Trusted code generation and verification to prevent fraud from maleficent external devices that capture data

ABSTRACT

A user equipment. The user equipment comprises a processor, a memory, a trusted security zone, wherein the trusted security zone provides hardware assisted trust, a ticket generator stored in the trusted security zone to generate a plurality of access codes, and a code generator stored in the trusted security zone. The code generator generates a different one-time-password for each of the plurality of access codes, wherein the one-time-password is not displayed on the user equipment, stores the one-time-password in the trusted security zone, and transmits the one-time-password to a trusted server through a trusted channel. Responsive to an associated access code from the plurality of access codes being displayed and upon request of a user of the user equipment, the code generator displays the one-time-password and invalidates the one-time-password promptly after the display ends.

CROSS-REFERENCE TO RELATED APPLICATIONS

None.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Network capable electronic devices are becoming increasingly prevalent in our daily lives. With the rapid development and popularization of network capable electronic devices, applications on the network capable electronic devices are growing rapidly. For example, people can now order, pay for, obtain, and redeem digital tickets on network capable mobile communication devices.

SUMMARY

In an embodiment, a user equipment is disclosed. The user equipment comprises a processor, a memory, a trusted security zone, wherein the trusted security zone provides hardware assisted trust, a ticket generator stored in the trusted security zone to generate a plurality of access codes, and a code generator stored in the trusted security zone. The code generator generates a different one-time-password for each of the plurality of access codes, wherein the one-time-password is not displayed on the user equipment, stores the one-time-password in the trusted security zone, and transmits the one-time-password to a trusted server through a trusted channel. Responsive to an associated access code from the plurality of access codes being displayed and upon request of a user of the user equipment, the code generator further displays the one-time-password and invalidates the one-time-password promptly after the display ends.

In an embodiment, a method of generating and verifying one-time-passwords for user equipments is disclosed. The method comprises generating, by a code generator stored in a trusted security zone in a memory of a user equipment, a different one-time-password associated with each of a plurality of access codes, wherein the trusted security zone provides hardware assisted trust, wherein the one-time-password is not displayed on the user equipment at the time of generation, and storing the one-time-password in the trusted security zone. The method further comprises transmitting the generated one-time-password to a trusted server through a trusted channel, and responsive to an associated access code being displayed at a point of sale (POS), displaying the one-time-password. The method further comprises transmitting, by the POS, a request to the trusted server for a one-time-password associated with the access code, and comparing the one-time-password displayed on the user equipment with the one-time-password received from the trusted server. The method further comprises responsive to the associated access code having been verified and the one-time-passwords matching, granting access associated with the access code to the user equipment, and invalidating the one-time-password promptly after the display ends.

In an embodiment, a method of generating and verifying one-time-passwords for user equipments is disclosed. The method comprises generating, by a code generator stored in a trusted security zone in a memory of a user equipment, a different one-time-password associated with each of a plurality of access codes, wherein the one-time-password is not displayed on the user equipment, and storing the one-time-password in the trusted security zone. The method further comprises transmitting the generated one-time-password to a trusted server through an encrypted channel, and responsive to an associated access code being displayed to a work station, transmitting the one-time-password to the work station through a dedicated channel, wherein the one-time-password is not displayed on the user equipment or the work station. The method further comprises transmitting, by the work station, a request to the trusted server for a one-time-password associated with the access code, comparing the one-time-password received from the user equipment with the one-time-password received from the trusted server, and examining the access code. The method further comprises responsive to the associated access code having been verified and the one-time-passwords from the user equipment and the trusted server matching, granting access associated with the access code to the user equipment, and invalidating the one-time-password after granting access to the user equipment.

These and other features will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.

FIG. 1 is an illustration of a communication system according to an embodiment of the disclosure.

FIG. 2 is a flow chart illustrating a method according to an embodiment of the disclosure.

FIG. 3 is a flow chart illustrating another method according to an embodiment of the disclosure.

FIG. 4 is an illustration of a user equipment to an embodiment of the disclosure.

FIG. 5 is a block diagram of a user equipment according to an embodiment of the disclosure.

FIG. 6A is a block diagram of a software architecture of a user equipment according to an embodiment of the disclosure.

FIG. 6B is a block diagram of another software architecture of a user equipment according to an embodiment of the disclosure.

FIG. 7 is a block diagram of a computer system according to an embodiment of the disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrative implementations of one or more embodiments are illustrated below, the disclosed systems and methods may be implemented using any number of techniques, whether currently known or not yet in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, but may be modified within the scope of the appended claims along with their full scope of equivalents.

User equipments may present digital tickets or e-tickets in a visual manner, for example as a number, a barcode, a quick response (QR) code, or in some other visual manner on a display of the user equipment. E-tickets may be vulnerable to shoulder-surfing with external cameras. For example, someone may take a video or photograph with an external camera of keyboard entry of an e-ticket on a user equipment. Alternatively, the person may use the external camera to capture a screenshot of the user equipment with e-ticket information displayed on the screen of the user equipment. The present disclosure teaches a system and method for generating one-time-passwords to prevent fraud from maleficent external devices that capture data.

For example, a code generator application in a trusted security zone in a memory of a user equipment may generate a one-time-password associated with an access token or an access code when the access code is obtained. The access code may be a flight e-ticket, a sports event e-ticket, a music event e-ticket, a hotel room reservation, secure space access, or another type of access code. For example, in the case where the access code is a flight e-ticket, when the flight e-ticket is purchased and/or generated, the code generator may generate a one-time-password associated with the flight e-ticket. For a second access code, a second one-time-password may be generated by the code generator.

A one-time-password may be generated by the code generator as a random number, for example using a random number generating algorithm or a pseudorandom number generating algorithm. The one-time-password may not be displayed at the time of generation. Furthermore, the one-time-password may not be displayed until the final use of the one-time-password or may not be displayed at all. For example, when a user and/or owner of the user equipment checks the e-ticket on the user equipment, the one-time-password may not be displayed. After the one-time-password is generated, it may be stored in the trusted security zone on the user equipment.

The one-time-password may also be transmitted to a trusted server by the code generator along with the association with the access code in a trusted and/or encrypted channel. For more details on establishing trusted end-to-end communication links relying on hardware assisted security, see U.S. patent application Ser. No. 13/532,588, filed Jun. 25, 2012, entitled “End-to-end Trusted Communications Infrastructure,” by Leo Michael McRoberts, et al., which is hereby incorporated by reference in its entirety. The trusted server may store the one-time-passwords with the associated access codes, for example on the trusted server itself or in a data store. It should be noted that although a user equipment with a trusted security zone is discussed throughout the disclosure as a preferred embodiment, the technology discussed in this disclosure may also be applied to user equipments without a trusted security zone enablement.

When the access code is displayed to be redeemed, for example when a flight e-ticket is displayed at a boarding counter, the one-time-password may be used. The one-time-password may be displayed or hidden when it is used. For example, the one-time-password may be displayed when the access code is displayed and an access agent (e.g., airline boarding agent) may read the one-time-password and enter it into a work station. Alternatively, the one-time-password may be received or read from the user equipment by the work station at the boarding counter without the one-time-password being displayed when the access code is displayed. For example, the one-time-password may be transmitted by the code generator from the user equipment to the work station using near field communication (NFC), WiFi direct, Bluetooth®, or some other non-visual method. When the work station obtains information of the one-time-password and the access code, the work station may transmit a request to the trusted server in order to verify whether or not the one-time-password is valid.

For example, the work station may request for a one-time-password on record associated with the displayed access code, for example by transmitting a request to the trusted server. The trusted server may locate the associated one-time-password based on the access code received from the work station and transmit the located one-time-password and the access code back to the work station. When the one-time-password from the trusted server and the one-time-password from the user equipment match, the one-time-password from the user equipment is determined by the work station to be valid. Alternatively, the work station may transmit to the trusted server both the access code and the associated one-time-password obtained from the user equipment. The trusted server may locate the associated one-time-password stored in the trusted server itself or in the data store based on the access code and compare the one-time-password received from the work station with the one-time-password on record. When the one-time-password stored by the trusted server and the one-time-password received from the work station match, the one-time-password from the work station (originally from the user equipment) is determined by the trusted server to be valid. The access code may be determined by the work station to be valid or not in traditional way(s) as in existing systems.

When both the access code and the one-time-password received from the user equipment are determined to be valid, access associated with the access code may be granted by the work station to the user equipment. Otherwise, access associated with the access code may be denied to the user equipment. The one-time-password may be invalidated by the code generator after use upon receipt of a command from the trusted server. For example, the one-time-password may be deleted, flagged as invalid, or invalidated in some other manner by the code generator. The trusted server may also invalidate the one-time-password at its side. For example, the trusted server may delete the stored one-time-password, flag the stored one-time-password as invalid, or invalidate the stored one-time-password in some other manner.

Turning now to FIG. 1, a communication system 100 is described. In an embodiment, the communication system 100 comprises a plurality of user equipments 124, a data store 106, and a trusted server 102. The trusted server 102 may comprise a server trusted security zone 104. The user equipment may alternatively be referred to in some contexts as a mobile communication device. The user equipment 124 may comprise a processor 108, an operating system 122, and a memory 120. The memory 120 may comprise a trusted security zone portion 110 and a permissive sector 118. The trusted security zone 110 may comprise a plurality of trusted applications 128, a code generator 112, and a ticket generator 114. The permissive sector 118 may comprise a plurality of non-trusted applications 116. The user equipment 124 may be configured to use a radio transceiver to establish a wireless communication link with an enhanced Node B (eNB) 130, and the eNB 130 may provide communications connectivity of the UE 124 to a network 126. The eNB may alternatively be referred to in some contexts as a base transceiver station (BTS). The trusted server 102 and the data store 106 may also have access to the network 126. The network 126 may comprise any combination of private and public networks.

It is understood that the system 100 may comprise any number of user equipments 124, any number of data stores 106, and any number of eNBs 130. The collectivity of eNBs 130 may be said to comprise a radio access network, in that these eNBs 130 may provide a radio communication link to the user equipments 124 to provide access to the network 126. The radio transceiver of the user equipment 124 may communicate with the eNB 130 using any of a variety of wireless communication protocols including a code division multiple access (CDMA) wireless communication protocol, a global system for mobile communication (GSM) wireless communication protocol, a long-term evolution (LTE) wireless communication protocol, a world-wide interoperability for microwave access (WiMAX) wireless communication protocol, or another wireless communication protocol.

While a user equipment or smart phone is used in a preferred embodiment, the teachings of the present disclosure may also be extended to other mobile communication devices such as a laptop computer, a notebook computer, a tablet computer, a mobile phone, a personal digital assistant (PDA), a media player, a headset computer, a wearable computer, a game console, an Internet digital media streaming device, a television, or another network/communications capable device. In an embodiment, the user equipment 124 may have other components (not shown) such as a near field communication (NFC) radio transceiver, a short range radio transceiver such as a wireless local area network radio transceiver, or other components.

The trusted server 102 and the data store 106 may be server computers. The trusted server 102 and the data store 106 may be located in one computer—for example a server computer, in two different computers—for example, a server computer for the trusted server 102 and another computer for the data store 106, in multiple different computers—for example, multiple server computers for the trusted server 102 and other multiple computers for the data store 106, or in some other combination of computers. When the trusted server 102 and the data store 106 are not located in one computer, the trusted server 102 and the data store 106 may share the same wired or wireless local area network.

Non-trusted applications 116 are normal applications on the user equipment 124. When trusted applications 128 are executed in the trusted security zone 110 of the user equipment 124, peripherals and data of the user equipment 124 may not be accessible to the non-trusted applications 116. The non-trusted applications 116 may be stored in a permissive sector 118 in the memory 120. The permissive sector 118 of the memory 120 is the normal partition in the memory 120. Additionally, non-secure resources may be stored in the permissive sector 118 in the memory 120.

The trusted security zone 110 may be implemented by partitioning both hardware and software resources of the user equipment 124 into two partitions: a secure partition and a normal partition. The secure partition may be implemented by a distinct, separate, or dedicated physical processor, usually the first processor, from the processor by which the normal partition may be implemented, usually the second processor. Alternatively, the secure partition may be implemented by a distinct, separate, or dedicated virtual processor from the virtual processor by which the normal partition may be implemented. A server trusted security zone 104 may be a server-side trusted security zone and may communicate with the trusted security zone 110 and/or applications on the user equipment 124.

The code generator 112 may be a trusted application and may be stored in the trusted security zone 110 of the user equipment 124. When executed by the processor 108, the code generator 112 may perform a variety of functionality associated with one-time-passwords 134. For example, the code generator 112 may generate a one-time-password 134 associated with each of a plurality of access codes. The code generator 112 may store the generated one-time-password 134 and/or transmit the one-time-password 134 to the trusted server 102. The code generator 112 may display the one-time-password 134 under predefined circumstances or may exchange the one-time-password 134 with a ticket verification system. Additionally, the code generator 112 may invalidate the one-time-password 134 after the display or exchange upon request from the trusted server 102.

For example, a one-time-password 134 may be generated by the code generator 112 for each access code. The one-time-password 134 may be generated by the code generator 112 as a random number, a group of characters, or any combination of the two, for example using a random number generating algorithm or a pseudorandom number generating algorithm. The random number generating algorithm may use some seed with a difficult to know value, such as the 16 lowest bits of a counter in the user equipment 124, a global positioning system (GPS) coordinate, or a short sequence of bits from a recently taken photograph. The one-time-password 134 may be generated by the code generator 112 based on a number chosen by the trusted server 102, for example using the number chosen by the trusted server 102 as a random seed for the random number generating algorithm or the pseudorandom number generating algorithm. The one-time-password 134 may be generated by the code generator 112 based on a previously generated one-time-password 134, for example using the previously generated one-time-password 134 as a random seed for the random number generating algorithm or the pseudorandom number generating algorithm. Alternatively, the one-time-password 134 may be generated by the code generator 112 based on time-synchronization between the trusted server 102 and the user equipment 124.

The one-time-password 134 may be integrated by the code generator 112 into a file that constitutes the associated access code, for example in text. For example, if the access code is generated as a barcode, the information of the one-time-password 134 may also be integrated or embedded in the barcode. When the barcode is scanned by a ticket agent under predefined circumstances, for example at a specific point of sale (POS), the scanner may extract information of the associated one-time-password 134. For example, the barcode may comprise information of the one-time-password 134 and the scanner may access the trusted security zone 110 to obtain the one-time-password 134 from the trusted security zone 110, for example through an application programming interface (API).

Alternatively, the one-time-password 134 may be generated by the code generator 112 in a way that the one-time-password 134 is separate from a file that constitutes the associated access code. For example, the one-time-password 134 may be generated in a second file separate from a first file that constitutes the access code. In an embodiment, the second file may be coupled to the first file. In another embodiment, the access code may be in the form of a quick response (QR) code and the QR code may comprise a marker, indicator, or pointer pointing to the one-time-password 134.

A plurality of one-time-passwords 134 may be generated at once or at various times. For example, the plurality of one-time-passwords 134 may be generated by the code generator 112 at the same time and may be used at different times. This method of generating a plurality of one-time-passwords 134 at once and using them at various times may be beneficial when the user equipment 124 does not always have access to the network 126 and may not be able to communicate with the trusted server 102 at times. For example, for a flight e-ticket, two one-time-passwords 134 may be generated by the code generator 112 when the e-ticket is purchased and/or generated. Here the flight e-ticket may be an access code. One of the two one-time-passwords 134 may be used at a transportation security administration (TSA) checkpoint at an airport with the e-ticket and/or an identification (ID) document such as a driver's license or a passport. The other one-time-password 134 may be used at a boarding counter with the flight e-ticket right before boarding. With more than one one-time password generated at once, the user equipment 124 and the trusted server 102 may synchronize to use and/or invalidate the one-time-passwords 134. For example, each one-time-password 134 may be configured to have a time-to-live (TTL) value.

Alternatively, one-time-passwords 134 may be generated by the code generator 112 at various times. For example, a first one-time-password 134 may be generated by the code generator 112 at the time when the flight e-ticket is purchased and/or generated. The first one-time-password 134 may be used at the transportation security administration checkpoint at the airport with the flight e-ticket and/or an identification document. A second one-time-password 134 may be generated at a corresponding boarding counter when the e-ticket is displayed to a ticket agent. The second one-time-password 134 may be used at the boarding counter when the flight e-ticket is displayed to the ticket agent.

The one-time-password 134 may not be displayed on the user equipment 124 at the time of generation. The one-time-password 134 may be stored by the code generator 112 in the trusted security zone 110 after the one-time-password 134 is generated. The generated one-time-password 134 may be transmitted by the code generator 112 with the associated access code to the trusted server 102 through a trusted channel. The trusted server 102 may store the received one-time-password 134 and/or the association with the access code in the trusted server 102. Alternatively, the trusted server 102 may store the received one-time-password 134 and/or the association with the access code in the data store 106.

The one-time-password 134 may be used or redeemed by the code generator 112 under predefined circumstances. The one-time-password 134 may be displayed or may be hidden when the one-time-password 134 is used. For example, when the one-time-password 134 is used, it may be displayed on the user equipment 124 or on a work station 132. The work station 132 may be a ticket verification machine. Alternatively, when the one-time-password 134 is used, it may be hidden, e.g., the one-time-password 134 may not be displayed on the user equipment 124 or the work station 132. Instead, information of the one-time-password 134 may be exchanged between the user equipment 124 and the work station 132. For example, information of the one-time-password 134 stored in the trusted security zone 110 of the user equipment 124 may be integrated in or coupled to the associated access code. When the access code is read by the work station 132, the embedded or coupled information of the one-time-password 134 may be obtained by the work station 132 without a visual representation of the one-time-password 134 being shown. The verification process of the one-time-password 134 is similar with the two cases: when the one-time-password 134 is displayed and when the one-time-password 134 is not displayed.

For example, the one-time-password 134 may be displayed or used by the code generator 112 upon request by an owner and/or a user of the user equipment 124. The one-time-password 134 may be displayed or used by the code generator 112 upon receipt of a code, for example a code that is input by the owner and/or user of the user equipment 124. In an embodiment, this code may be different from the access code. For example, the code may be a personal identification number (PIN) of the user equipment 124. The one-time-password 134 may be displayed or used by the code generator 112 based on a location-based service, for example when the location-based service detects that the user equipment 124 is at a specific POS location. For example, if the access code is a flight e-ticket of American Airlines, an associated one-time-password 134 may be displayed or used by the code generator 112 when the location-based service detects that the user equipment 124 is at an American Airlines boarding counter at a specific airport based on the departure information of the e-ticket.

A work station 132 at the boarding counter may verify the access code and the associated one-time-password 134. For example, the work station 132 may read the access code and the associated one-time-password 134. When the one-time-password 134 is not displayed, the work station 132 may receive information of the one-time-password 134 from the user equipment 124 or read information of the one-time-password 134 from the user equipment 124. The work station 132 may verify the access code in the manner that is performed in currently existing systems. When the access code is verified to be valid, the work station 132 may further transmit a request to the trusted server 102 for a one-time-password 134 b associated with the verified access code. For example, the work station 132 may transmit a message to the trusted server 102 with the access code requesting for an associated one-time-password 134 b.

The trusted server 102 may look up the associated one-time-password 134 b, for example in a stored bank of one-time-password(s) 134 b and association with access code(s), based on the access code received from the work station 132. When the stored associated one-time-password 134 b is located, the trusted server 102 may transmit the located one-time-password 134 b with the access code back to the work station 132. After the located one-time-password 134 b is received from the trusted server 102, the work station 132 may compare the one-time-password 134 b received from the trusted server 102 with the one-time-password 134 a displayed on the user equipment 124. The work station 132 may further compare the one-time-password 134 a received from the user equipment 124 with the one-time-password 134 b received from the trusted server 102. When the one-time-password 134 b received from the trusted server 102 matches the one-time-password 134 a from the user equipment 124, the one-time-password 134 a from the user equipment 124 is determined by the work station 132 to be valid.

Alternatively, when the access code is verified to be valid, the work station 132 may transmit to the trusted server 102 the displayed access code and the one-time-password 134 a read and/or received from the user equipment 124. The trusted server 102 may compare the pair of the one-time-password 134 a and the access code received from the work station 132 with stored pair(s) of one-time-password(s) 134 b and access code(s) to determine whether or not the one-time-password 134 a from the work station 132 is valid. For example, the trusted server 102 may locate a record of the pair of the one-time-password 134 b and the associated access code based on the access code received from the work station 132. The trusted server 102 may compare the located one-time-password 134 b in the record with the one-time-password 134 a received from the work station 132. When the located one-time-password 134 b in the record matches the one-time-password 134 a received from the work station 132, the one-time-password 134 a from the work station 132 which originates from the user equipment 124 is determined by the trusted server 102 to be valid. The trusted server 102 may transmit a message to the work station 132 confirming the validity of the one-time-password 134 a from the user equipment 124.

When both the access code and the one-time-password 134 a from the user equipment 124 are verified to be valid, access associated with the access code may be granted by the work station 132 to the user equipment 124. Otherwise, access associated with the access code may be denied by the work station 132 to the user equipment 124. For example, if the access code from the user equipment 124 is determined to be invalid, access may be denied by the work station 132 to the user equipment 124. If the access code from the user equipment 124 is determined to be valid but the one-time-password 134 a from the user equipment 124 is determined to be invalid, access may be denied by the work station 132 to the user equipment 124.

In an embodiment, the one-time-password 134 may be invalidated promptly after the use, for example within one minute after the user, within 30 seconds after the use, or within another short period of time after the use. The one-time-password 134 may be invalidated after the one-time-password 134 is verified to be valid and the associated access is granted to the user equipment 124. Additionally, the one-time-password 134 may be invalidated when the one-time-password 134 is verified to be invalid and the associated access is denied to the user equipment 124. For example, the trusted server 102 may transmit a command to the user equipment 124, for example to the code generator 112 or some other trusted application 128 in the trusted security zone 110, to invalidate the used one-time-password 134. The command may be received by the user equipment 124 through an application programming interface. The one-time-password 134 may be deleted, flagged as invalid, or invalidated in some other manner. The code generator 112 may transmit an acknowledgement message back to the trusted server 102 after the one-time-password 134 has been invalidated. Additionally, the trusted server 102 may also invalidate the one-time-password 134 stored on the trusted server 102 or the data store 106, for example by deleting the one-time-password 134, flagging the one-time-password 134 as invalid, or invalidating the one-time-password 134 in some other manner.

Turning now to FIG. 2, a method 200 is described. At block 202, a different one-time-password 134 for each of a plurality of access codes is generated by a code generator stored in a trusted security zone in a memory of a user equipment, wherein the trusted security zone provides hardware assisted trust, wherein the one-time-password 134 is not displayed on the user equipment at the time of generation. For example, a different one-time-password 134 associated with each of a plurality of access codes may be generated by the code generator 112 stored in the trusted security zone 110 of the user equipment 124. At block 204, the one-time-password 134 is stored in the trusted security zone 110.

At block 206, the generated one-time-password 134 is transmitted to the trusted server 102 through a trusted channel. At block 208, responsive to an associated access code being displayed at a point of sale (POS), the one-time-password 134 a is displayed. At block 210, a request is transmitted by the POS to the trusted server 102 for a one-time-password 134 b associated with the access code.

At block 212, the one-time-password 134 a displayed on the user equipment 124 is compared with the one-time-password 134 b received from the trusted server 102. At block 214, responsive to the associated access code having been verified and the one-time-passwords 134 a and 134 b matching, access associated with the access code is granted to the user equipment 124. At block 216, the one-time-password 134 is invalidated promptly after the display ends. For example, the one-time-password 134 is deleted from the user equipment 124 and from the trusted server 102.

Turning now to FIG. 3, a method 300 is described. At block 302, a different one-time-password 134 associated with each of a plurality of access codes is generated by the code generator 112 stored in a trusted security zone 110 in a memory 120 of a user equipment 124, wherein the one-time-password 134 is not displayed on the user equipment 124. At block 304, the one-time-password 134 is stored in the trusted security zone 110.

At block 306, the generated one-time-password 134 is transmitted to a trusted server 102 through an encrypted channel. For example, the one-time-password 134 may be encrypted using an encryption key and transmitted over a communication channel to the trusted server 102. Upon receipt of the encrypted one-time-password 134, the trusted server 102 may decrypt the encrypted one-time-password 134 using an appropriate key. At block 308, responsive to an associated access code being displayed to a work station 132, the one-time-password 134 a is transmitted to the work station 132 through a dedicated channel, wherein the one-time-password 134 a is not displayed on the user equipment 124 or the work station 132. For example, the one-time-password 134 a may be transmitted by the code generator 112 from the user equipment 124 to the work station 132 using near field communication (NFC), WiFi direct, Bluetooth®, or some other dedicated channel. At block 310, a request is transmitted by the work station 132 to the trusted server 102 for a one-time-password 134 b associated with the access code.

At block 312, the one-time-password 134 a received from the user equipment 124 is compared with the one-time-password 134 b received from the trusted server 102. At block 314, the access code is examined. At block 316, responsive to the associated access code having been verified and the one-time-passwords 134 a and 134 b from the user equipment 124 and the trusted server 102 respectively matching, access associated with the access code is granted to the user equipment 124. At block 318, the one-time-password 134 is invalidated after granting access to the user equipment 124.

FIG. 4 depicts the user equipment (UE) 400, which is operable for implementing aspects of the present disclosure, but the present disclosure should not be limited to these implementations. Though illustrated as a mobile phone, the UE 400 may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a gaming device, or a media player. The UE 400 includes a touchscreen display 402 having a touch-sensitive surface for input by a user. A small number of application icons 404 are illustrated within the touch screen display 402. It is understood that in different embodiments, any number of application icons 404 may be presented in the touch screen display 402. In some embodiments of the UE 400, a user may be able to download and install additional applications on the UE 400, and an icon associated with such downloaded and installed applications may be added to the touch screen display 402 or to an alternative screen. The UE 400 may have other components such as electro-mechanical switches, speakers, camera lenses, microphones, input and/or output connectors, and other components as are well known in the art. The UE 400 may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct. The UE 400 may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the handset. The UE 400 may further execute one or more software or firmware applications in response to user commands. These applications may configure the UE 400 to perform various customized functions in response to user interaction. Additionally, the UE 400 may be programmed and/or configured over-the-air, for example from a wireless base station, a wireless access point, or a peer UE 400. The UE 400 may execute a web browser application which enables the touch screen display 402 to show a web page. The web page may be obtained via wireless communications with a base transceiver station, a wireless network access node, a peer UE 400 or any other wireless communication network or system.

FIG. 5 shows a block diagram of the UE 400. While a variety of known components of handsets are depicted, in an embodiment a subset of the listed components and/or additional components not listed may be included in the UE 400. The UE 400 includes a digital signal processor (DSP) 502 and a memory 504. As shown, the UE 400 may further include an antenna and front end unit 506, a radio frequency (RF) transceiver 508, a baseband processing unit 510, a microphone 512, an earpiece speaker 514, a headset port 516, an input/output interface 518, a removable memory card 520, a universal serial bus (USB) port 522, an infrared port 524, a vibrator 526, one or more electro-mechanical switches 528, a touch screen liquid crystal display (LCD) with a touch screen display 530, a touch screen/LCD controller 532, a camera 534, a camera controller 536, and a global positioning system (GPS) receiver 538. In an embodiment, the UE 400 may include another kind of display that does not provide a touch sensitive screen. In an embodiment, the UE 400 may include both the touch screen display 530 and additional display component that does not provide a touch sensitive screen. In an embodiment, the DSP 502 may communicate directly with the memory 504 without passing through the input/output interface 518. Additionally, in an embodiment, the UE 400 may comprise other peripheral devices that provide other functionality.

The DSP 502 or some other form of controller or central processing unit operates to control the various components of the UE 400 in accordance with embedded software or firmware stored in memory 504 or stored in memory contained within the DSP 502 itself. In addition to the embedded software or firmware, the DSP 502 may execute other applications stored in the memory 504 or made available via information carrier media such as portable data storage media like the removable memory card 520 or via wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP 502 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 502.

The DSP 502 may communicate with a wireless network via the analog baseband processing unit 510. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input/output interface 518 interconnects the DSP 502 and various memories and interfaces. The memory 504 and the removable memory card 520 may provide software and data to configure the operation of the DSP 502. Among the interfaces may be the USB port 522 and the infrared port 524. The USB port 522 may enable the UE 400 to function as a peripheral device to exchange information with a personal computer or other computer system. The infrared port 524 and other optional ports such as a Bluetooth® interface or an IEEE 802.11 compliant wireless interface may enable the UE 400 to communicate wirelessly with other nearby handsets and/or wireless base stations. In an embodiment, the UE 400 may comprise a near field communication (NFC) transceiver. The NFC transceiver may be used to complete payment transactions with point-of-sale terminals or other communications exchanges. In an embodiment, the UE 400 may comprise a radio frequency identify (RFID) reader and/or writer device.

The switches 528 may couple to the DSP 502 via the input/output interface 518 to provide one mechanism for the user to provide input to the UE 400. Alternatively, one or more of the switches 528 may be coupled to a motherboard of the UE 400 and/or to components of the UE 400 via a different path (e.g., not via the input/output interface 518), for example coupled to a power control circuit (power button) of the UE 400. The touch screen display 530 is another input mechanism, which further displays text and/or graphics to the user. The touch screen LCD controller 532 couples the DSP 502 to the touch screen display 530. The GPS receiver 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the UE 400 to determine its position.

FIG. 6A illustrates a software environment 602 that may be implemented by the DSP 502. The DSP 502 executes operating system software 604 that provides a platform from which the rest of the software operates. The operating system software 604 may provide a variety of drivers for the handset hardware with standardized interfaces that are accessible to application software. The operating system software 604 may be coupled to and interact with application management services (AMS) 606 that transfer control between applications running on the user equipment 400. Also shown in FIG. 6A are a web browser application 608, a media player application 610, and JAVA applets 612. The web browser application 608 may be executed by the user equipment 400 to browse content and/or the Internet, for example when the user equipment 400 is coupled to a network via a wireless link. The web browser application 608 may permit a user to enter information into forms and select links to retrieve and view web pages. The media player application 610 may be executed by the user equipment 400 to play audio or audiovisual media. The JAVA applets 612 may be executed by the user equipment 400 to provide a variety of functionality including games, utilities, and other functionality.

FIG. 6B illustrates an alternative software environment 620 that may be implemented by the DSP 502. The DSP 502 executes operating system kernel (OS kernel) 628 and an execution runtime 630. The DSP 502 executes applications 622 that may execute in the execution runtime 630 and may rely upon services provided by the application framework 624. Applications 622 and the application framework 624 may rely upon functionality provided via the libraries 626.

A trusted security zone provides chipsets with a hardware root of trust, a secure execution environment for applications, and secure access to peripherals. A hardware root of trust means the chipset should only execute programs intended by the device manufacturer or vendor and resists software and physical attacks, and therefore remains trusted to provide the intended level of security. The chipset architecture is designed to promote a programmable environment that allows the confidentiality and integrity of assets to be protected from specific attacks. Trusted security zone capabilities are becoming features in both wireless and fixed hardware architecture designs. Providing the trusted security zone in the main user equipment chipset and protecting the hardware root of trust removes the need for separate secure hardware to authenticate the device or user. To ensure the integrity of the applications requiring trusted data, such as a mobile financial services application, the trusted security zone also provides the secure execution environment where only trusted applications can operate, safe from attacks. Security is further promoted by restricting access of non-trusted applications to peripherals, such as data inputs and data outputs, while a trusted application is running in the secure execution environment. In an embodiment, the trusted security zone may be conceptualized as hardware assisted security.

A complete Trusted Execution Environment (TEE) may be implemented through the use of the trusted security zone hardware and software architecture. The Trusted Execution Environment is an execution environment that is parallel to the execution environment of the main user equipment operating system. The Trusted Execution Environment and/or the trusted security zone may provide a base layer of functionality and/or utilities for use of applications that may execute in the trusted security zone. For example, in an embodiment, trust tokens may be generated by the base layer of functionality and/or utilities of the Trusted Execution Environment and/or trusted security zone for use in trusted end-to-end communication links to document a continuity of trust of the communications. Through standardization of application programming interfaces (APIs), the Trusted Execution Environment becomes a place to which scalable deployment of secure services can be targeted. A device which has a chipset that has a Trusted Execution Environment on it may exist in a trusted services environment, where devices in the trusted services environment are trusted and protected against attacks. The Trusted Execution Environment can be implemented on mobile phones and tablets as well as extending to other trusted devices such as personal computers, servers, sensors, medical devices, point-of-sale terminals, industrial automation, handheld terminals, automotive, etc.

The trusted security zone is implemented by partitioning all of the hardware and software resources of the user equipment into two partitions: a secure partition and a normal partition. The secure partition may be implemented by a first physical processor, and the normal partition may be implemented by a second physical processor. Alternatively, the secure partition may be implemented by a first virtual processor, and the normal partition may be implemented by a second virtual processor. Placing sensitive resources in the secure partition can protect against possible attacks on those resources. For example, resources such as trusted software applications may run in the secure partition and have access to hardware peripherals such as a touchscreen or a secure location in memory. Less secure peripherals such as wireless radios may be disabled completely while the secure partition is being accessed, while other peripherals may only be accessed from the secure partition. While the secure partition is being accessed through the Trusted Execution Environment, the main mobile operating system in the normal partition is suspended, and applications in the normal partition are prevented from accessing the secure peripherals and data. This prevents corrupted applications or malware applications from breaking the trust of the device.

The trusted security zone is implemented by partitioning the hardware and software resources to exist in a secure subsystem which is not accessible to components outside the secure subsystem. The trusted security zone is built into the processor architecture at the time of manufacture through hardware logic present in the trusted security zone which enables a perimeter boundary between the secure partition and the normal partition. The trusted security zone may only be manipulated by those with the proper credentials and, in an embodiment, may not be added to the chip after it is manufactured. Software architecture to support the secure partition may be provided through a dedicated secure kernel running trusted applications. Trusted applications are independent secure applications which can be accessed by normal applications through an application programming interface in the Trusted Execution Environment on a chipset that utilizes the trusted security zone.

In an embodiment, the normal partition applications run on a first virtual processor, and the secure partition applications run on a second virtual processor. Both virtual processors may run on a single physical processor, executing in a time-sliced fashion, removing the need for a dedicated physical security processor. Time-sliced execution comprises switching contexts between the two virtual processors to share processor resources based on tightly controlled mechanisms such as secure software instructions or hardware exceptions. The context of the currently running virtual processor is saved, the context of the virtual processor being switched to is restored, and processing is restarted in the restored virtual processor. Time-sliced execution protects the trusted security zone by stopping the execution of the normal partition while the secure partition is executing.

The two virtual processors context switch via a processor mode called monitor mode when changing the currently running virtual processor. The mechanisms by which the processor can enter monitor mode from the normal partition are tightly controlled. The entry to monitor mode can be triggered by software executing a dedicated instruction, the Secure Monitor Call (SMC) instruction, or by a subset of the hardware exception mechanisms such as hardware interrupts, which can be configured to cause the processor to switch into monitor mode. The software that executes within monitor mode then saves the context of the running virtual processor and switches to the secure virtual processor.

The trusted security zone runs a separate operating system that is not accessible to the device users. For security purposes, the trusted security zone is not open to users for installing applications, which means users do not have access to install applications in the trusted security zone. This prevents corrupted applications or malware applications from executing powerful instructions reserved to the trusted security zone and thus preserves the trust of the device. The security of the system is achieved at least in part by partitioning the hardware and software resources of the mobile phone so they exist in one of two partitions, the secure partition for the security subsystem and the normal partition for everything else. Placing the trusted security zone in the secure partition and restricting access from the normal partition protects against software and basic hardware attacks. Hardware logic ensures that no secure partition resources can be accessed by the normal partition components or applications. A dedicated secure partition operating system runs in a virtual processor separate from the normal partition operating system that likewise executes in its own virtual processor. Users may install applications on the user equipment which may execute in the normal partition operating system described above. The trusted security zone runs a separate operating system for the secure partition that is installed by the user equipment manufacturer or vendor, and users are not able to install new applications in or alter the contents of the trusted security zone.

FIG. 7 illustrates a computer system 380 suitable for implementing one or more embodiments disclosed herein. The computer system 380 includes a processor 382 (which may be referred to as a central processor unit or CPU) that is in communication with memory devices including secondary storage 384, read only memory (ROM) 386, random access memory (RAM) 388, input/output (I/O) devices 390, and network connectivity devices 392. The processor 382 may be implemented as one or more CPU chips.

It is understood that by programming and/or loading executable instructions onto the computer system 380, at least one of the CPU 382, the RAM 388, and the ROM 386 are changed, transforming the computer system 380 in part into a particular machine or apparatus having the novel functionality taught by the present disclosure. It is fundamental to the electrical engineering and software engineering arts that functionality that can be implemented by loading executable software into a computer can be converted to a hardware implementation by well-known design rules. Decisions between implementing a concept in software versus hardware typically hinge on considerations of stability of the design and numbers of units to be produced rather than any issues involved in translating from the software domain to the hardware domain. Generally, a design that is still subject to frequent change may be preferred to be implemented in software, because re-spinning a hardware implementation is more expensive than re-spinning a software design. Generally, a design that is stable that will be produced in large volume may be preferred to be implemented in hardware, for example in an application specific integrated circuit (ASIC), because for large production runs the hardware implementation may be less expensive than the software implementation. Often a design may be developed and tested in a software form and later transformed, by well-known design rules, to an equivalent hardware implementation in an application specific integrated circuit that hardwires the instructions of the software. In the same manner as a machine controlled by a new ASIC is a particular machine or apparatus, likewise a computer that has been programmed and/or loaded with executable instructions may be viewed as a particular machine or apparatus.

Additionally, after the system 380 is turned on or booted, the CPU 382 may execute a computer program or application. For example, the CPU 382 may execute software or firmware stored in the ROM 386 or stored in the RAM 388. In some cases, on boot and/or when the application is initiated, the CPU 382 may copy the application or portions of the application from the secondary storage 384 to the RAM 388 or to memory space within the CPU 382 itself, and the CPU 382 may then execute instructions that the application is comprised of. In some cases, the CPU 382 may copy the application or portions of the application from memory accessed via the network connectivity devices 392 or via the I/O devices 390 to the RAM 388 or to memory space within the CPU 382, and the CPU 382 may then execute instructions that the application is comprised of. During execution, an application may load instructions into the CPU 382, for example load some of the instructions of the application into a cache of the CPU 382. In some contexts, an application that is executed may be said to configure the CPU 382 to do something, e.g., to configure the CPU 382 to perform the function or functions promoted by the subject application. When the CPU 382 is configured in this way by the application, the CPU 382 becomes a specific purpose computer or a specific purpose machine.

The secondary storage 384 is typically comprised of one or more disk drives or tape drives and is used for non-volatile storage of data and as an over-flow data storage device if RAM 388 is not large enough to hold all working data. Secondary storage 384 may be used to store programs which are loaded into RAM 388 when such programs are selected for execution. The ROM 386 is used to store instructions and perhaps data which are read during program execution. ROM 386 is a non-volatile memory device which typically has a small memory capacity relative to the larger memory capacity of secondary storage 384. The RAM 388 is used to store volatile data and perhaps to store instructions. Access to both ROM 386 and RAM 388 is typically faster than to secondary storage 384. The secondary storage 384, the RAM 388, and/or the ROM 386 may be referred to in some contexts as computer readable storage media and/or non-transitory computer readable media.

I/O devices 390 may include printers, video monitors, liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, or other well-known input devices.

The network connectivity devices 392 may take the form of modems, modem banks, Ethernet cards, universal serial bus (USB) interface cards, serial interfaces, token ring cards, fiber distributed data interface (FDDI) cards, wireless local area network (WLAN) cards, radio transceiver cards that promote radio communications using protocols such as code division multiple access (CDMA), global system for mobile communications (GSM), long-term evolution (LTE), worldwide interoperability for microwave access (WiMAX), near field communications (NFC), radio frequency identity (RFID), and/or other air interface protocol radio transceiver cards, and other well-known network devices. These network connectivity devices 392 may enable the processor 382 to communicate with the Internet or one or more intranets. With such a network connection, it is contemplated that the processor 382 might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Such information, which is often represented as a sequence of instructions to be executed using processor 382, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.

Such information, which may include data or instructions to be executed using processor 382 for example, may be received from and outputted to the network, for example, in the form of a computer data baseband signal or signal embodied in a carrier wave. The baseband signal or signal embedded in the carrier wave, or other types of signals currently used or hereafter developed, may be generated according to several methods well-known to one skilled in the art. The baseband signal and/or signal embedded in the carrier wave may be referred to in some contexts as a transitory signal.

The processor 382 executes instructions, codes, computer programs, scripts which it accesses from hard disk, floppy disk, optical disk (these various disk based systems may all be considered secondary storage 384), flash drive, ROM 386, RAM 388, or the network connectivity devices 392. While only one processor 382 is shown, multiple processors may be present. Thus, while instructions may be discussed as executed by a processor, the instructions may be executed simultaneously, serially, or otherwise executed by one or multiple processors. Instructions, codes, computer programs, scripts, and/or data that may be accessed from the secondary storage 384, for example, hard drives, floppy disks, optical disks, and/or other device, the ROM 386, and/or the RAM 388 may be referred to in some contexts as non-transitory instructions and/or non-transitory information.

In an embodiment, the computer system 380 may comprise two or more computers in communication with each other that collaborate to perform a task. For example, but not by way of limitation, an application may be partitioned in such a way as to permit concurrent and/or parallel processing of the instructions of the application. Alternatively, the data processed by the application may be partitioned in such a way as to permit concurrent and/or parallel processing of different portions of a data set by the two or more computers. In an embodiment, virtualization software may be employed by the computer system 380 to provide the functionality of a number of servers that is not directly bound to the number of computers in the computer system 380. For example, virtualization software may provide twenty virtual servers on four physical computers. In an embodiment, the functionality disclosed above may be provided by executing the application and/or applications in a cloud computing environment. Cloud computing may comprise providing computing services via a network connection using dynamically scalable computing resources. Cloud computing may be supported, at least in part, by virtualization software. A cloud computing environment may be established by an enterprise and/or may be hired on an as-needed basis from a third party provider. Some cloud computing environments may comprise cloud computing resources owned and operated by the enterprise as well as cloud computing resources hired and/or leased from a third party provider.

In an embodiment, some or all of the functionality disclosed above may be provided as a computer program product. The computer program product may comprise one or more computer readable storage medium having computer usable program code embodied therein to implement the functionality disclosed above. The computer program product may comprise data structures, executable instructions, and other computer usable program code. The computer program product may be embodied in removable computer storage media and/or non-removable computer storage media. The removable computer readable storage medium may comprise, without limitation, a paper tape, a magnetic tape, magnetic disk, an optical disk, a solid state memory chip, for example analog magnetic tape, compact disk read only memory (CD-ROM) disks, floppy disks, jump drives, digital cards, multimedia cards, and others. The computer program product may be suitable for loading, by the computer system 380, at least portions of the contents of the computer program product to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380. The processor 382 may process the executable instructions and/or data structures in part by directly accessing the computer program product, for example by reading from a CD-ROM disk inserted into a disk drive peripheral of the computer system 380. Alternatively, the processor 382 may process the executable instructions and/or data structures by remotely accessing the computer program product, for example by downloading the executable instructions and/or data structures from a remote server through the network connectivity devices 392. The computer program product may comprise instructions that promote the loading and/or copying of data, data structures, files, and/or executable instructions to the secondary storage 384, to the ROM 386, to the RAM 388, and/or to other non-volatile memory and volatile memory of the computer system 380.

In some contexts, the secondary storage 384, the ROM 386, and the RAM 388 may be referred to as a non-transitory computer readable medium or a computer readable storage media. A dynamic RAM embodiment of the RAM 388, likewise, may be referred to as a non-transitory computer readable medium in that while the dynamic RAM receives electrical power and is operated in accordance with its design, for example during a period of time during which the computer system 380 is turned on and operational, the dynamic RAM stores information that is written to it. Similarly, the processor 382 may comprise an internal RAM, an internal ROM, a cache memory, and/or other internal non-transitory storage blocks, sections, or components that may be referred to in some contexts as non-transitory computer readable media or computer readable storage media.

While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted or not implemented.

Also, techniques, systems, subsystems, and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein. 

What is claimed is:
 1. A user equipment, comprising: a processor of the user equipment; a memory of the user equipment; a trusted security zone of the user equipment, wherein the trusted security zone provides hardware assisted trust and is implemented by partitioning hardware and software resources into a secure partition and a normal partition; a ticket generator stored in the secure partition in the trusted security zone of the user equipment to generate a plurality of access codes; and a code generator stored in the secure partition in the trusted security zone of the user equipment configured to: generate a different one-time-password for each of the plurality of access codes, wherein the one-time-password is not displayed on the user equipment, store the one-time-password in the secure partition in the trusted security zone, transmit the one-time-password to a trusted server through a trusted channel, wherein the one-time-password generated in the trusted security zone of the user equipment and received by the trusted server from the user equipment is stored in the trusted server, responsive to an associated access code from the plurality of access codes being displayed and upon request of a user of the user equipment, display the one-time-password, wherein a request is sent to the trusted server from a point of sale or a workstation for the one-time-password associated with the access code, and wherein access is granted to the user equipment in response to a verification of the associated access code and the one-time-password from the user equipment and the one-time-password stored by the trusted server matching, and invalidate the one-time-password promptly after the display ends.
 2. The user equipment of claim 1, wherein the one-time-password is integrated into a file that constitutes the associated access code in text.
 3. The user equipment of claim 1, wherein the one-time-password is separated from a file that constitutes the associated access code.
 4. The user equipment of claim 1, wherein the one-time-password is generated by a random number generating algorithm, and wherein the one-time-password is invalidated within one minute after the display ends.
 5. The user equipment of claim 4, wherein the one-time-password is generated based on a seed chosen by the trusted server.
 6. The user equipment of claim 4, wherein the one-time-password is generated based on a previously generated one-time-password.
 7. The user equipment of claim 4, wherein the one-time-password is generated based on time-synchronization between the trusted server and the user equipment.
 8. A method of generating and verifying one-time-passwords for user equipments, comprising: generating, by a code generator stored in a trusted security zone in a memory of a user equipment, a different one-time-password associated with each of a plurality of access codes, wherein the trusted security zone provides hardware assisted trust and is implemented by partitioning hardware and software resources into a secure partition and a normal partition, and wherein the one-time-password is not displayed on the user equipment at the time of generation; storing the one-time-password in the secure partition in the trusted security zone of the user equipment; transmitting the one-time-password to a trusted server through a trusted channel, wherein the one-time-password generated in the trusted security zone of the user equipment and received by the trusted server from the user equipment is stored in the trusted server; responsive to an associated access code being displayed at a point of sale (POS), displaying the one-time-password; transmitting, by the POS, a request to the trusted server for a one-time-password associated with the access code; comparing the one-time-password displayed on the user equipment with the one-time-password stored by and received from the trusted server; responsive to the associated access code having been verified and the one-time-password from the user equipment and the one-time-password stored by the trusted server matching, granting access associated with the access code to the user equipment; and invalidating the one-time-password promptly after the display ends.
 9. The method of claim 8, further comprising utilizing a location-based service to recognize the proper POS location to display the access code and the one-time-password.
 10. The method of claim 8, wherein the one-time-password is displayed upon request by a user of the user equipment.
 11. The method of claim 10, wherein the user of the user equipment enters a code for the code generator to display the one-time-password, and wherein the one-time-password is invalidated within 30 seconds after the display ends.
 12. The method of claim 8, wherein the access code is for at least one of a plane ticket, a sports event access, a music event access, a hotel room reservation, or a secure space access, and wherein the secure spaces access is secure access to one of a building, a floor, or a room.
 13. The method of claim 8, wherein the one-time-password is invalidated upon receipt of a command from the trusted server.
 14. The method of claim 13, wherein the command from the trusted server is received by the user equipment through an application programming interface (API).
 15. A method of generating and verifying one-time-passwords for user equipments, comprising: generating, by a code generator stored in a trusted security zone in a memory of a user equipment, a different one-time-password associated with each of a plurality of access codes, wherein the trusted security zone provides hardware assisted trust and is implemented by partitioning hardware and software resources into a secure partition and a normal partition, and wherein the one-time-password is not displayed on the user equipment; storing the one-time-password in the secure partition in the trusted security zone of the user equipment; transmitting the one-time-password to a trusted server through an encrypted channel, wherein the one-time-password generated in the trusted security zone of the user equipment and received by the trusted server from the user equipment is stored in the trusted server; responsive to an associated access code being displayed to a work station, transmitting the one-time-password to the work station through a dedicated channel, wherein the one-time-password is not displayed on the user equipment or the work station; transmitting, by the work station, a request to the trusted server for a one-time-password associated with the access code; comparing the one-time-password received from the user equipment with the one-time-password stored by and received from the trusted server; examining the access code; responsive to the associated access code having been verified and the one-time-password from the user equipment and the one-time-password stored by the trusted server matching, granting access associated with the access code to the user equipment; and invalidating the one-time-password after granting access to the user equipment.
 16. The method of claim 15, wherein the user equipment is one of a laptop computer, a notebook computer, a tablet computer, a mobile phone, a personal digital assistant (PDA), a media player, a headset computer, a wearable computer, a game console, an Internet digital media streaming device, a television, or another network/communications capable device.
 17. The method of claim 15, wherein the user equipment establishes a wireless communication with a radio access network according to a code division multiple access (CDMA) wireless communication protocol, a global system for mobile communication (GSM) wireless communication protocol, a long-term evolution (LTE) wireless communication protocol, or a world-wide interoperability for microwave access (WiMAX) wireless communication protocol.
 18. The method of claim 15, wherein the one-time-password is generated by a random number generating algorithm.
 19. The method of claim 18, wherein the one-time-password is generated based on a seed chosen by the trusted server.
 20. The method of claim 18, wherein the one-time-password is generated based on a previously generated one-time-password. 